I've seen this posted elsewhere but the proposed solutions don't apply to, or are simply 'solutions' we can't apply in this environment. We occasionaly see one or both of the following on desktops and laptops alike "Could not reconnect all network drives" balloon message and an icon in the system tray No balloon message but the icon exists in the system tray Understandably this happens off the network (although we want to suppress that), however, this happens while on the network. In every case that we've seen this, when we check 'Computer' (formerly 'My Computer'), all of the network drives are connected. Windows reports a 'false positive' - so to speak. Briefly here's our setup Win 7 Enterprise in a domain environemnt Built-in Win 7 firewall has been disabled No third-party software firewall solutions present We use a login script, however, the login script does not handle the mapping of all of our network drives. This is because we have a number of different departments, who, over the years, used overlapping drive letters and there are some situations where users also overlap departments that use overlapping drive letters. (This goes back before my time.) So instead, users map their own drives, remember the credentials and reconnect at logon. Furthermore, when users call the Help Desk, the Help Desk uses the '/persistent:yes' switch/parameter when doing mappinv via command line. Not sure if this is relevant, but, when we move users to a new machine, or reimage their machine, we backup & restore the HKCU\Network key, which houses the mapped connections, to make the transition nearly seamless. (So, doing a `net use * /delete /Y` to 'fix' this problem is not an option here.) Is there anything I can do to to prevent that message from popping up along with preventing the icon from displaying in the system tray? Although the "Always wait for the network at computer startup and logon" and "Turn off all balloon notifications" GPO settings are set to 'Enabled', those are the only potentially relevant GPO setting I could find, and they don't appear to fix this issue. Also, I've been looking at the setting discussed here http://support.microsoft.com/kb/937624/en-us but although users are promoted to local administrators via a GPO I'm not certain that applies here or if that will help. Lastly, thanks to another post I found on the forums, I ran across this setting http://support.microsoft.com/kb/297684 and am wondering if this is worth investigating, however, I'm concerned of how changing this setting may affect the servers the user's are connecting to based on way this sentence was phrased: "This behavior occurs because the systems can drop idle connections after a specified time-out period (by default, 15 minutes) to prevent wasting server resources on unused sessions. " If we set this value to some insanely high value (65535), how might that impact a server with a 1000 connections? Any suggestions are greatly appreciated.